layer: Fix query of capabilities of aliased extensions #474
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
christophe-lunarg
added
bug
|
CI VulkanProfiles build # 2689 running. |
1 similar comment
|
CI VulkanProfiles build # 2689 running. |
|
CI VulkanProfiles build # 2689 passed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This issue was find when using a profile requiring
VK_EXT_mutable_descriptor_type, when querying the required capabilities inVkPhysicalDeviceMutableDescriptorTypeFeaturesEXTthe structure was empty because the layer would only check with the aliased extensionVK_VALVE_mutable_descriptor_type,